Monitoring vehicle usage

ABSTRACT

A method for monitoring vehicle usage is described. In one embodiment, the method includes detecting a vehicle event and detecting a query from a mobile device. The query includes a Wi-Fi probe request or Bluetooth inquiry. The method includes identifying a mobile device identifier from the query and associating the mobile device identifier with the vehicle event.

BACKGROUND

Advancements in media delivery systems and data-related technologiescontinue to increase at a rapid pace. Increasing demand for accessibledata has influenced the advances made to data-related technologies.Computer systems have increasingly become an integral part of datacreation, data usage, and data storage. Computer systems may be used tocarry out several data-related functions. The wide-spread access to datahas been accelerated by the increased use of computer networks,including the Internet and cloud networking.

Many homes and businesses use one or more computer networks to generate,deliver, and receive data and information between the various computersconnected to computer networks. Users of computer technologies continueto demand increased access to information and an increase in theefficiency of these technologies. Improving the efficiency of computertechnologies is desirable to those who use and rely on computers.

With the wide-spread use of computers and mobile devices has come anincreased presence of and continued advancements in data monitoringtechnologies. For example, advancements in mobile devices allow users tomonitor a home or business from anywhere in the world.

SUMMARY

According to at least one embodiment, a method for monitoring vehicleusage is described. In one embodiment, the method may include detectinga vehicle event and detecting a query from a mobile device. The querymay include a Wi-Fi probe request or Bluetooth inquiry. The method mayinclude identifying a mobile device identifier from the query andassociating the mobile device identifier with the vehicle event. In somecases, the vehicle event is detected in conjunction with an on-boarddiagnostic (OBD) connector.

In some embodiments, the mobile device identifier includes anycombination of a device serial number, international mobile equipmentidentity (IMEI) number, mobile equipment identifier (MEID), cellulardata number (CDN), integrated circuit card identifier (ICCID), Wi-Fimedia access control (MAC) address, BLUETOOTH® MAC address, BLUETOOTH®global identifier, carrier information, mobile device model information,and a list of service set identifiers (SSIDs). In some cases, thevehicle event includes any combination of vehicle speed, vehicleacceleration, vehicle deceleration, vehicle braking, vehiclegravitational force (g-force), vehicle seat belt use, distance traveled,engine performance, vehicle occupancy, and vehicle location.

In one embodiment, the method may include determining whether the mobiledevice is within the vehicle. Determining whether the mobile device iswithin the vehicle may include any combination of satisfying a quantityof queries threshold, satisfying a query timing threshold, andsatisfying a signal strength threshold. In some cases, the methodincludes identifying excessive behavior from the vehicle event. Theexcessive behavior may include any combination of satisfying a speedthreshold, satisfying an acceleration threshold, satisfying adeceleration threshold, satisfying a braking threshold, satisfying ag-force threshold, satisfying a revolutions per minute (RPM) threshold,and satisfying an audio system volume threshold.

In some cases, the method may include associating the mobile deviceidentifier with the excessive behavior and/or associating the mobiledevice identifier with an identity of a vehicle occupant. Upon detectinga predetermined mobile device identifier, an operation of the vehiclemay be altered and/or an alert notification may be generated. In oneembodiment, the method include storing the mobile device identifier anddata associated with the mobile device identifier in a cloud dataservice. The mobile device identifier and associations of the mobiledevice identifier may be communicated to the cloud data service via acellular link.

A computing device configured for monitoring vehicle usage is alsodescribed. The computing device may include a processor and memory inelectronic communication with the processor. The memory may storecomputer executable instructions that when executed by the processorcause the processor to perform the steps of detecting a vehicle event,detecting a query from a mobile device, identifying a mobile deviceidentifier from the query, and associating the mobile device identifierwith the vehicle event. In some cases, the query include a Wi-Fi proberequest or Bluetooth inquiry.

A non-transitory computer-readable storage medium storing computerexecutable instructions is also described. When the instructions areexecuted by a processor, the execution of the instructions may cause theprocessor to perform the steps of detecting a vehicle event, detecting aquery from a mobile device, identifying a mobile device identifier fromthe query, and associating the mobile device identifier with the vehicleevent. In some cases, the query include a Wi-Fi probe request orBluetooth inquiry.

Features from any of the above-mentioned embodiments may be used incombination with one another in accordance with the general principlesdescribed herein. These and other embodiments, features, and advantageswill be more fully understood upon reading the following detaileddescription in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate a number of exemplary embodimentsand are a part of the specification. Together with the followingdescription, these drawings demonstrate and explain various principlesof the instant disclosure.

FIG. 1 is a block diagram illustrating one embodiment of an environmentin which the present systems and methods may be implemented;

FIG. 2 is a block diagram illustrating one example of a vehiclemonitoring module;

FIG. 3 is a block diagram illustrating one example of an environment formonitoring vehicle usage for the timely notification of vehicle-relatedevents;

FIG. 4 is a block diagram illustrating one example of vehicle datagathered from monitoring vehicle usage;

FIG. 5 is a flow diagram illustrating one embodiment of a method formonitoring vehicle usage;

FIG. 6 is a flow diagram illustrating one embodiment of a method formonitoring vehicle usage; and

FIG. 7 depicts a block diagram of a computer system suitable forimplementing the present systems and methods.

While the embodiments described herein are susceptible to variousmodifications and alternative forms, specific embodiments have beenshown by way of example in the drawings and will be described in detailherein. However, the exemplary embodiments described herein are notintended to be limited to the particular forms disclosed. Rather, theinstant disclosure covers all modifications, equivalents, andalternatives falling within the scope of the appended claims.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

The systems and methods described herein relate to vehicle monitoringsystems. More specifically, the systems and methods described hereinrelate to monitoring vehicle usage in relation to detectable vehicleevents. Some embodiments of the systems and methods described hereinrelate to monitoring vehicle usage in relation to detectable vehicleevents such as vehicle speed, vehicle seat belt use, vehicle location,vehicle gravitational force (g-force), vehicle occupancy, occupantidentity, and the like.

As one example, parents of children that are relatively new to drivingrealize that the driving behavior of their children may be influencedthrough peer pressure. When the child is driving with the parent, thechild may be cautious and adhere to motor vehicle laws and follow thestandards of safe driving. When the child is driving with certain peers,the child's driving behavior may become excessive. For instance, thechild may feel pressured to exceed speed limits, and take others risksthat the child would not have otherwise taken. On the other hand, thechild's driving behavior may be acceptable when driving with otherpeers. The parent may use vehicle data devices to gather data regardingthe child's driving behavior. Such devices may tell the parent if thedriving behavior of the child needs correcting. The parent, however, maynot know the underlying circumstances of the excessive behavior.Accordingly, the present systems and methods may indicate to the parentnot only excessive behavior, but also identification of the vehicleoccupants when the excessive behavior occurs. If the parent knew whenthe child was more likely to drive excessively, such as when certainpeers are occupants when the child is driving the vehicle, then theparent may be notified and be enabled to use this information to resolvethe issue. In one embodiment, the present systems and methods may beperformed in conjunction with a vehicle on-board diagnostic system, avehicle computing system, a data communication system, and/or anon-board diagnostics dongle. On-board diagnostics (OBD) is an automotiveterm referring to a vehicle's self-diagnostic and reporting capability.OBD systems provide access to the status of various vehicle systems.Modern OBD implementations may use a standardized digital communicationsport to provide real-time data in addition to a standardized series ofdiagnostic trouble codes (DTCs), which allow one to rapidly identify andremedy malfunctions within the vehicle.

FIG. 1 is a block diagram illustrating one embodiment of an environment100 in which the present systems and methods may be implemented. In someembodiments, the systems and methods described herein may be performedon a device (e.g., device 105). As depicted, the environment 100 mayinclude a device 105, server 110, a sensor 125, a display 130, acomputing device 150, an automation controller 155, and a network 115that allows the device 105, the server 110, the computing device 150,automation controller 155, and sensor 125 to communicate with oneanother.

In some embodiments, device 105 may be part of one or more components ofa vehicle. Examples of the device 105 may include any combination of OBDdongles, vehicle computer systems, mobile devices, smart phones,personal computing devices, computers, laptops, desktops, servers, andthe like. In some cases, device 105 may include a vehicle diagnosticsystem integrated within device 105 and/or may be in communication witha vehicle diagnostic system. In some embodiments, device 105 may includeone or more processors, memory, storage devices, and/or datacommunication devices. Device 105 may be part of a vehicle computersystem and/or in communication with a vehicle computer system.

Examples of automation controller 155 may include any device configuredto control a building such as a home, a business, a government facility,etc. Accordingly, examples of automation controller 155 include anycombination of a dedicated building automation computing device (e.g.,wall-mounted controller), a personal computing device (e.g., laptop,desktop, etc.), a mobile computing device (e.g., tablet computingdevice, smartphone, etc.), and the like. In some cases, device 105 maybe configured to send data to automation controller 155. For example,vehicle data captured via device 105 may be sent and made available fordisplay on a display of automation controller 155.

Examples of computing device 150 may include any combination of a mobilecomputing device, a laptop, a desktop, a server, a media set top box,etc. Examples of server 110 may include any combination of a dataserver, a cloud server, a server associated with an automation serviceprovider, proxy server, mail server, web server, application server,database server, communications server, file server, home server, mobileserver, name server, and the like.

Examples of sensor 125 may include any combination of a speed sensor,acceleration sensor, deceleration sensor, gravitational force (g-force)sensor, braking sensor, seat belt sensor, odometer sensor, enginetemperature sensor, engine oil level sensor, engine oil temperaturesensor, engine timing sensor, engine revolutions per minute (RPM)sensor, fuel injector sensor, fuel use sensor, miles per gallon (MPG)sensor, seat occupancy sensor, location sensor (e.g., global positioningsystem (GPS), wireless triangulation, etc.), audio decibel sensor,camera sensor, forced entry sensor, shock sensor, proximity sensor,boundary sensor, light beam sensor, glass break sensor, door sensor,window sensor, other types of sensors, actuators, or combinationsthereof. Sensor 125 may represent one or more separate sensors or acombination of two or more sensors in a single device. For example,sensor 125 may represent one or more camera sensors and one or moreengine data sensors connected to environment 100. Sensor 125 may beintegrated with an identity detection system such as a facialrecognition system and/or a voice recognition system. Although sensor125 is depicted as connecting to device 105 over network 115, in someembodiments, sensor 125 may connect directly to or within device 105.

Additionally, or alternatively, sensor 125 may be integrated with avehicle system, such as a car stereo system, vehicle GPS system, vehicleclimate system. For example, sensor 125 may be installed on the dash ofa vehicle. In some cases, sensor 125 may include a camera installed in arear-view mirror in addition to other cameras. Sensor 125 may include awireless communication sensor 125 configured to send and receive dataand/or information to and from one or more devices in environment 100.Additionally, or alternatively, sensor 125 may include a GPS sensor toenable sensor 125 to track a location of the vehicle. In someembodiments, sensor 125 may include a forced entry sensor (e.g., shocksensor, glass break sensor, etc.) to enable sensor 125 to detect anattempt to break into the vehicle. Sensor 125 may include a siren tosound an alarm, etc.

In some configurations, the device 105 may include a user interface 135,application 140, and vehicle monitoring module 145. Although thecomponents of the device 105 are depicted as being internal to thedevice 105, it is understood that one or more of the components may beexternal to the device 105 and connect to device 105 through wiredand/or wireless connections. In some embodiments, application 140 may beinstalled on computing device 150 in order to allow a user to interfacewith a function of device 105, vehicle monitoring module 145, automationcontroller 155, and/or server 110.

In some embodiments, device 105 may communicate with server 110 vianetwork 115. Example of networks 115 may include any combination ofcloud networks, local area networks (LAN), wide area networks (WAN),virtual private networks (VPN), wireless networks (using 802.11, forexample), cellular networks (using 3G and/or LTE, for example), etc. Insome configurations, the network 115 may include the Internet. It isnoted that in some embodiments, the device 105 may not include a vehiclemonitoring module 145. For example, device 105 may include application140 that allows device 105 to interface with automation controller 155via vehicle monitoring module 145 located on another device such ascomputing device 150 and/or server 110. In some embodiments, device 105,automation controller 155, and server 110 may include a vehiclemonitoring module 145 where at least a portion of the functions ofvehicle monitoring module 145 are performed separately and/orconcurrently on device 105, automation controller 155, and/or server110. Likewise, in some embodiments, a user may access the functions ofdevice 105 and/or automation controller 155 (directly or through device105 via vehicle monitoring module 145) from computing device 150. Forexample, in some embodiments, computing device 150 includes a mobileapplication that interfaces with one or more functions of device 105,automation controller 155, vehicle monitoring module 145, and/or server110.

In some embodiments, server 110 may be coupled to database 120. Database120 may be internal or external to the server 110. In one example,device 105 may be coupled directly to database 120, database 120 beinginternal or external to device 105. Database 120 may include vehicledata 160. For example, device 105 may access vehicle data 160 indatabase 120 over network 115 via server 110. Vehicle data 160 mayinclude data generated by sensor 125. For example, vehicle data 160 mayinclude data regarding vehicle performance, vehicle speed, vehicleacceleration, and the like. Vehicle data 160 may include mobile deviceidentifiers detected by device 105 via vehicle monitoring module 145. Insome cases, vehicle data 160 may include associations between vehicledata, excessive driving data, mobile device identifiers, identities ofvehicle occupants, and the like. Accordingly, vehicle monitoring module145 may enable a user to track vehicle data, excessive driving data, andmobile device identifiers indicating mobile devices that were detectedas being within the vehicle at the time the vehicle data was detected.Further details regarding the vehicle monitoring module 145 arediscussed below.

FIG. 2 is a block diagram illustrating one example of a vehiclemonitoring module 145-a. Vehicle monitoring module 145-a may be oneexample of vehicle monitoring module 145 depicted in FIG. 1. Asdepicted, vehicle monitoring module 145-a may include vehicle eventmodule 205, an identification module 210, data module 215, modificationmodule 220, and a notification module 225.

In one embodiment, vehicle event module 205 may detect a vehicle event.The vehicle event may include any combination of vehicle speed, vehicleacceleration, vehicle deceleration, vehicle braking, vehiclegravitational force (g-force), vehicle seat belt use, distance traveled,engine performance, vehicle occupancy, and vehicle location. Vehiclelocation may be determined by any combination of radio directionfinding, radio triangulation, terrestrial radio positioning systemsutilizing a Low Frequency (LF) switched packet radio network, localpositioning system (LPS), and GPS. Engine performance may include anycombination of fuel consumption, miles per gallon of fuel, oiltemperature, engine revolutions per minute (RPM), engine timingperformance, and the like.

In some cases, the vehicle event is detected in conjunction with anon-board diagnostic (OBD) connector. In some embodiments, vehicle eventmodule 205 may identify excessive behavior from the vehicle event.Identifying excessive behavior may include any combination of satisfyinga speed threshold, satisfying an acceleration threshold, satisfying adeceleration threshold, satisfying a braking threshold (e.g., hardbraking events such as a deceleration of 0.40 g or greater), satisfyinga g-force threshold, satisfying a revolutions per minute (RPM)threshold, and satisfying an audio system volume threshold. For example,vehicle event module 205 may compare detected vehicle events to one ormore thresholds. For instance, one speed threshold may include travelingat a speed above 70 miles per hour. When vehicle event module 205detects the vehicle traveling at and/or above 70 miles per hour, vehicleevent module 205 may detect the speed and identify that the detectedspeed satisfies at least one speed threshold. In some cases, the one ormore thresholds may be location dependent. For example, a speedthreshold of 70 miles per hour may apply when the vehicle is detected asoperating on an interstate or highway, and a speed threshold of 30 milesper hour may apply when the vehicle is detected as operating within aresidential area.

In one embodiment, identification module 210 may detect a query from amobile device, the query comprising a Wi-Fi probe request or BLUETOOTH®inquiry. A mobile device may generate a Wi-Fi probe request for thepurpose of detecting external Wi-Fi access points, base stations, nodes,etc. Typically, a Wi-Fi device within range of the mobile device mayreply with a probe response. Likewise, a BLUETOOTH® device may respondto the BLUETOOTH® inquiry with an inquiry response. Mobile deviceidentifier detection may include passive and/or active scanning.Accordingly, using active scanning, identification module 210 mayactively scan for mobile devices with Wi-Fi enabled, listening forinformation provided by the mobile device and/or requesting informationfrom the mobile device. Additionally, or alternatively, using passivescanning, identification module 210 may wait for a mobile device to senda query (e.g., Wi-Fi probe request and/or BLUETOOTH® inquiry) and gatherinformation from the query.

In some embodiments, identification module 210 may only include thosecomponents used to identify identification information associated withthe device from the query. For example, the identification module 210may include and/or make use of a stripped-down version of a Wi-Fi accesspoint and/or BLUETOOTH® access point, such as an access point thatincludes only an antenna, a decoder, a processor, and memory. Thus, insome embodiments, other elements used by access points to receive andsend data from a back end to a user end device may be absent from theidentification module 210. Alternatively, in some cases, theidentification module 210 includes and/or makes use of afully-functional access point. Accordingly, in some embodiments,identification module 210 may identify a mobile device identifier fromthe query. The mobile device identifier may include any combination of adevice serial number, international mobile equipment identity (IMEI)number, mobile equipment identifier (MEID), cellular data number (CDN),integrated circuit card identifier (ICCID), Wi-Fi media access control(MAC) address, BLUETOOTH® MAC address, BLUETOOTH® global identifier,carrier information, mobile device model information, and a list ofservice set identifiers (SSIDs). In one embodiment, identificationmodule 210 may identify an occupant of the vehicle. Identificationmodule 210 may use any combination of voice recognition, facialrecognition, data entry, and the like to identify an occupant of thevehicle. In some cases, identification module 210 may identify anoccupant using a previously established association between a mobiledevice identifier and an identity of an occupant.

In one embodiment, identification module 210 may determine whether themobile device is within the vehicle. In some cases, identificationmodule 210 may determine whether the mobile device is within the vehiclevia any combination of satisfying a quantity of queries threshold,satisfying a query timing threshold, and satisfying a signal strengththreshold. For example, if the query includes a predetermined number ofqueries, then the query may satisfy a quantity of queries threshold.Additionally, or alternatively, if the query includes multiple queriesover a predetermined time threshold, then the query may satisfy a querytiming threshold. Additionally, or alternatively, if a signal of thequery satisfies a minimum signal strength, then the query may satisfy asignal strength threshold. In some embodiments, if a variation in thesignal strength over time varies within a predetermined maximumvariation, then the query may satisfy a signal strength threshold. Forexample, with a maximum variation of 1 decibel (dB), if the initialsignal strength of a query is 3 dB and the signal strength remainsbetween 2.1 dB and 3.9 dB, then the most the query varies is 0.9 dB,which is within the 1 dB threshold, and so the signal strength thresholdmay be satisfied. Additionally, or alternatively, a signal strength ofthe query may be measured while the engine is idle and/or when thevehicle is in motion. In some cases, the signal strength while idlingmay be compared to the signal strength while in motion. If the signalstrength remains within a predetermined signal strength range, then thequery may satisfy a signal strength threshold. Additionally, oralternatively, if signal strength remains within a predetermined signalstrength range while the vehicle is in motion, then the query maysatisfy a signal strength threshold.

In one embodiment, data module 215 may associate the mobile deviceidentifier with a vehicle event. For example, the data module 215 mayassociate that mobile device identifier X and mobile device identifier Ywere detected when the vehicle was driven from point A to point B. Insome cases, data module 215 may associate the mobile device identifierwith excessive behavior identified from the vehicle events. Thus, whenexcessive speed is detected, data module 215 may associate mobile deviceidentifiers X and Y with the excessive speed. In some cases, data module215 may associate the mobile device identifier with an identity of avehicle occupant.

In one embodiment, data module 215 may store the mobile deviceidentifier and data associated with the mobile device identifier in acloud data service. For example, the data module 215 may associate anidentity with the mobile device identifier. Thus, the data module 215may transmit the identity and mobile device identifier to the cloud dataservice for storage and retrieval. In some cases, data module 215 maysend to the cloud data service associations between the mobile deviceidentifier, vehicle occupant identity, detected vehicle data, and/orexcessive behavior. In some cases, the mobile device identifier andassociations of the mobile device identifier may be communicated to thecloud data service via a cellular link. For example, the vehicle mayinclude an integrated cellular communication device. The data module 215may utilize the vehicle's cellular-enabled device to communicate themobile device and vehicle-related data to the cloud data service.Additionally, or alternatively, vehicle monitoring module 145-a and/ordevice 105 may include a cellular communication device. Accordingly,patterns may be detectable regarding the stored associations of vehicledata, excessive behavior, and mobile device identifiers. For example, aparent may want to track the driving behavior of a child. When the childdrives with the parent, the vehicle data may indicate no excessivebehavior. When the child drives with one friend, however, the vehicledata may indicate at least some excessive behavior, while when the childdrives with another friend, again the vehicle data indicates noexcessive behavior. Accordingly, the parent may want to be notified whencertain people are in the vehicle with the parent's child.

Upon detecting a predetermined mobile device identifier, notificationmodule 225 may generate an alert notification. The notification may besent in real-time upon detecting notification triggers (e.g., vehicleevents, mobile device identifiers, etc.). The notification may includeany combination of an identifier of a mobile device detected within thevehicle, an identity associated with the identifier of the mobiledevice, a vehicle event history report associated with the identifier ofthe mobile device, an image captured by a camera on the vehicle, and thelike. Additionally, or alternatively, upon detecting a predeterminedmobile device identifier, indicating a certain person is within thevehicle, modification module 220 may alter an operation of the vehicle.For example, in some cases, modification module 220 may immobilize thevehicle. In some cases, modification module 220 may govern or limit thespeed of the vehicle. In some embodiments, modification module 220 mayconditionally immobilize the vehicle until one or more conditions aremet. For example, the modification module 220 may immobilize the vehicleuntil seat belts are worn, until an identifiable occupant leaves thevehicle, until an identifiable occupant enters the vehicle, until apredetermined user is notified, until a predetermined user authorizesuse of the vehicle, etc.

FIG. 3 is a block diagram illustrating one example of an environment 300for monitoring vehicle usage for the timely notification ofvehicle-related events. As depicted, a vehicle 305 may be configured asdepicted to include an identification sensor 310, a vehicle sensor 315,a camera 320, a data transceiver 325, and on-board diagnostics 330. Asdepicted, each element 310-330 within vehicle 305 may be configured tocommunicate over a bus, such that each element 310-330 may communicatewith each other. In some cases, each element 310-330 may be elements ofa single device. Alternatively, one or more of the elements 310-330 maybe part of a separate device. Any combination of elements 310-330 may beincluded in and/or work in conjunction with vehicle monitoring module145-a.

In one embodiment, the identification sensor 310 may identify a mobiledevice identifier, such as a WiFi MAC address and/or a BLUETOOTH® MACaddress. For example, an occupant of vehicle 305 may carry a smartphonethat communicates a query for available Wi-Fi and/or BLUETOOTH® accesspoints. Accordingly, identification sensor 310 may identify informationin the query that identifies the smartphone. In some cases, camera 320may capture one or more images of an interior view of vehicle 305. Insome cases, vehicle 305 may include two or more cameras to capturedifferent views. In some embodiments, identification sensor 310 mayassociate an image captured by camera 320 with identified mobile deviceidentifiers.

In one embodiment, vehicle sensor 315 may identify one or more vehicleevents of vehicle 305, such as vehicle occupancy, seat belt use, vehiclespeed, vehicle acceleration, vehicle deceleration, etc. On-boarddiagnostics 330 may include a connector that connects to an OBD port ofvehicle 305. On-board diagnostics 330 may include one or moreprocessors, memory, and a storage device. Accordingly, on-boarddiagnostics 330 may process the detected vehicle events and/or theidentified mobile device identifiers. For example, on-board diagnostics330 may associate a vehicle event with a mobile device identifier. Datatransceiver 325 may communicate data such as detected vehicle events,captured images, identified mobile device identifiers, and/orassociations between such data to an external database (e.g., database120). For example, database 120 may be a database hosted on cloud dataservice 335.

FIG. 4 is a block diagram illustrating one example of vehicle data 400gathered from monitoring vehicle usage. Vehicle data 400 may be oneexample of vehicle data 160 depicted in FIG. 1. Additionally, oralternatively, vehicle data 400 may be one example of the data of FIG. 3detected and gathered at vehicle 305 and communicated to cloud dataservice 335.

As depicted, vehicle data 400 may organized with a title bar 405indicating that the data displayed includes “Vehicle Data.” The vehicledata may be sorted according to displayed headers 410. Some examples ofheaders 410 may include “Mobile Device ID,” “Associated Vehicle Events,”and “Identity.” As illustrated, vehicle data 400 may include dataentries 415. For example, a first data entry from data entries 415 mayinclude a mobile device identifier of “88:53:95:4b:05:02,” which mayrepresent a Wi-Fi MAC address, associated vehicle events of “ExcessiveSpeed” and “Excessive Braking” and an identity of “R. Smith” beingassociated with the mobile device identifier. Data entries 415 may alsoinclude entries for other mobile device identifiers such as BLUETOOTH®MAC addresses (e.g., “88:53:95:4b:05:02”), IMEI number (e.g.,“49-015420-323751”), model number (e.g., “MD658LL/A”), serial number(e.g., “88846THXH7H”), and the like. If no excessive vehicle events aredetected in association with a mobile device identifier, vehicle data400 may indicate this by stating, for example, “Normal operation” asillustrated. Likewise, if a mobile device identifier is not associatedwith a known identity, vehicle data 400 may indicate this by stating,for example, “Unknown” as illustrated.

FIG. 5 is a flow diagram illustrating one embodiment of a method 500 formonitoring vehicle usage. In some configurations, the method 500 may beimplemented by the vehicle monitoring module 145 illustrated in FIG. 1or 2. In some configurations, the method 500 may be implemented inconjunction with the application 140 and/or the user interface 135illustrated in FIG. 1.

At block 505, a vehicle event may be detected. The vehicle event mayinclude any combination of vehicle speed, vehicle acceleration, vehicledeceleration, vehicle braking, vehicle gravitational force (g-force),vehicle seat belt use, distance traveled, engine performance, vehicleoccupancy, and vehicle location. The vehicle event may be detected inconjunction with an on-board diagnostic (OBD) connector. At block 510, aquery from a mobile device may be detected. The query may include aWi-Fi probe request or Bluetooth inquiry. At block 515, a mobile deviceidentifier may be identified from the query. The mobile deviceidentifier may include any combination of a device serial number, IMEInumber, MEID number, CDN identifier, ICCID, Wi-Fi MAC address,BLUETOOTH® MAC address, BLUETOOTH® global identifier, carrierinformation, mobile device model information, and a list of SSIDs. Atblock 520, the mobile device identifier may be associated with thevehicle event.

FIG. 6 is a flow diagram illustrating one embodiment of a method 600 formonitoring vehicle usage. In some configurations, the method 600 may beimplemented by the vehicle monitoring module 145 illustrated in FIGS. 1and/or 2. In some configurations, the method 600 may be implemented inconjunction with the application 140 and/or the user interface 135illustrated in FIG. 1.

At block 605, a mobile device identifier may be identified from a query.At block 610, excessive behavior may be identified from a detectedvehicle event. The excessive behavior may include any combination ofsatisfying a speed threshold, satisfying an acceleration threshold,satisfying a deceleration threshold, satisfying a braking threshold,satisfying a g-force threshold, satisfying a revolutions per minute(RPM) threshold, and satisfying an audio system volume threshold. Atblock 615, the mobile device identifier may be associated with theexcessive behavior. At block 620, the mobile device identifier and dataassociated with the mobile device identifier may be stored in a clouddata service. At block 625, upon detecting a predetermined mobile deviceidentifier, an alert notification may be generated. In some cases, anoperation of the vehicle may be altered as a result of detecting thepredetermined mobile device identifier.

FIG. 7 depicts a block diagram of a controller 700 suitable forimplementing the present systems and methods. The controller 700 may bean example of device 105, computing device 150, and/or automationcontroller 155 illustrated in FIG. 1. In one configuration, controller700 includes a bus 705 which interconnects major subsystems ofcontroller 700, such as a central processor 710, a system memory 715(typically RAM, but which may also include ROM, flash RAM, or the like),an input/output controller 720, an external audio device, such as aspeaker system 725 via an audio output interface 730, an externaldevice, such as a display screen 735 via display adapter 740, an inputdevice 745 (e.g., remote control device interfaced with an inputcontroller 750), multiple USB devices 765 (interfaced with a USBcontroller 770), and a storage interface 780. Also included are at leastone sensor 755 connected to bus 705 through a sensor controller 760 anda network interface 785 (coupled directly to bus 705).

Bus 705 allows data communication between central processor 710 andsystem memory 715, which may include read-only memory (ROM) or flashmemory (neither shown), and random access memory (RAM) (not shown), aspreviously noted. The RAM is generally the main memory into which theoperating system and application programs are loaded. The ROM or flashmemory can contain, among other code, the Basic Input-Output system(BIOS) which controls basic hardware operation such as the interactionwith peripheral components or devices. For example, the vehiclemonitoring module 145-b to implement the present systems and methods maybe stored within the system memory 715. Applications (e.g., application140) resident with controller 700 are generally stored on and accessedvia a non-transitory computer readable medium, such as a hard disk drive(e.g., fixed disk 775) or other storage medium. Additionally,applications can be in the form of electronic signals modulated inaccordance with the application and data communication technology whenaccessed via interface 785.

Storage interface 780, as with the other storage interfaces ofcontroller 700, can connect to a standard computer readable medium forstorage and/or retrieval of information, such as a fixed disk drive 775.Fixed disk drive 775 may be a part of controller 700 or may be separateand accessed through other interface systems. Network interface 785 mayprovide a direct connection to a remote server via a direct network linkto the Internet via a POP (point of presence). Network interface 785 mayprovide such connection using wireless techniques, including digitalcellular telephone connection, Cellular Digital Packet Data (CDPD)connection, digital satellite data connection, or the like. In someembodiments, one or more sensors (e.g., motion sensor, smoke sensor,glass break sensor, door sensor, window sensor, carbon monoxide sensor,and the like) connect to controller 700 wirelessly via network interface785.

Many other devices or subsystems (not shown) may be connected in asimilar manner (e.g., entertainment system, computing device, remotecameras, wireless key fob, wall mounted user interface device, cellradio module, battery, alarm siren, door lock, lighting system,thermostat, home appliance monitor, utility equipment monitor, and soon). Conversely, all of the devices shown in FIG. 7 need not be presentto practice the present systems and methods. The devices and subsystemscan be interconnected in different ways from that shown in FIG. 7. Theaspect of some operations of a system such as that shown in FIG. 7 arereadily known in the art and are not discussed in detail in thisapplication. Code to implement the present disclosure can be stored in anon-transitory computer-readable medium such as one or more of systemmemory 715 or fixed disk 775. The operating system provided oncontroller 700 may be iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®,UNIX®, LINUX® or another known operating system.

Moreover, regarding the signals described herein, those skilled in theart will recognize that a signal can be directly transmitted from afirst block to a second block, or a signal can be modified (e.g.,amplified, attenuated, delayed, latched, buffered, inverted, filtered,or otherwise modified) between the blocks. Although the signals of theabove described embodiment are characterized as transmitted from oneblock to the next, other embodiments of the present systems and methodsmay include modified signals in place of such directly transmittedsignals as long as the informational and/or functional aspect of thesignal is transmitted between blocks. To some extent, a signal input ata second block can be conceptualized as a second signal derived from afirst signal output from a first block due to physical limitations ofthe circuitry involved (e.g., there will inevitably be some attenuationand delay). Therefore, as used herein, a second signal derived from afirst signal includes the first signal or any modifications to the firstsignal, whether due to circuit limitations or due to passage throughother circuit elements which do not change the informational and/orfinal functional aspect of the first signal.

While the foregoing disclosure sets forth various embodiments usingspecific block diagrams, flowcharts, and examples, each block diagramcomponent, flowchart step, operation, and/or component described and/orillustrated herein may be implemented, individually and/or collectively,using a wide range of hardware, software, or firmware (or anycombination thereof) configurations. In addition, any disclosure ofcomponents contained within other components should be consideredexemplary in nature since many other architectures can be implemented toachieve the same functionality.

The process parameters and sequence of steps described and/orillustrated herein are given by way of example only and can be varied asdesired. For example, while the steps illustrated and/or describedherein may be shown or discussed in a particular order, these steps donot necessarily need to be performed in the order illustrated ordiscussed. The various exemplary methods described and/or illustratedherein may also omit one or more of the steps described or illustratedherein or include additional steps in addition to those disclosed.

Furthermore, while various embodiments have been described and/orillustrated herein in the context of fully functional computing systems,one or more of these exemplary embodiments may be distributed as aprogram product in a variety of forms, regardless of the particular typeof computer-readable media used to actually carry out the distribution.The embodiments disclosed herein may also be implemented using softwaremodules that perform certain tasks. These software modules may includescript, batch, or other executable files that may be stored on acomputer-readable storage medium or in a computing system. In someembodiments, these software modules may configure a computing system toperform one or more of the exemplary embodiments disclosed herein.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the present systems and methods and their practicalapplications, to thereby enable others skilled in the art to bestutilize the present systems and methods and various embodiments withvarious modifications as may be suited to the particular usecontemplated.

Unless otherwise noted, the terms “a” or “an,” as used in thespecification and claims, are to be construed as meaning “at least oneof.” In addition, for ease of use, the words “including” and “having,”as used in the specification and claims, are interchangeable with andhave the same meaning as the word “comprising.” In addition, the term“based on” as used in the specification and the claims is to beconstrued as meaning “based at least upon.”

What is claimed is:
 1. A method for monitoring events within a vehicle,comprising: detecting, by a processor, a vehicle event; detecting, bythe processor, a query from a first mobile device and a second mobiledevice, the queries each comprising a Wi-Fi probe request or Bluetoothinquiry; identifying, by the processor, a mobile device identifier fromeach of the queries; and associating, by the processor, each of themobile device identifiers with the vehicle event.
 2. The method of claim1, wherein the mobile device identifier includes any combination of adevice serial number, international mobile equipment identity (IMEI)number, mobile equipment identifier (MEID), cellular data number (CDN),integrated circuit card identifier (ICCID), Wi-Fi media access control(MAC) address, BLUETOOTH® MAC address, BLUETOOTH® global identifier,carrier information, mobile device model information, and a list ofservice set identifiers (SSIDs).
 3. The method of claim 1, wherein thevehicle event comprises any combination of vehicle speed, vehicleacceleration, vehicle deceleration, vehicle braking, vehiclegravitational force (g-force), vehicle seat belt use, distance traveled,engine performance, vehicle occupancy, and vehicle location.
 4. Themethod of claim 1, further comprising: determining, by the processor,whether the first mobile device is within the vehicle, whereindetermining whether the first mobile device is within the vehiclecomprises any combination of satisfying a quantity of queries threshold,satisfying a query timing threshold, and satisfying a signal strengththreshold.
 5. The method of claim 1, further comprising: identifying, bythe processor, excessive behavior from the vehicle event, the excessivebehavior comprising any combination of satisfying a speed threshold,satisfying an acceleration threshold, satisfying a decelerationthreshold, satisfying a braking threshold, satisfying a g-forcethreshold, satisfying a revolutions per minute (RPM) threshold, andsatisfying an audio system volume threshold.
 6. The method of claim 5,further comprising: associating, by the processor, each of the mobiledevice identifiers with the excessive behavior.
 7. The method of claim1, further comprising: associating, by the processor, each of the mobiledevice identifiers with an identity of a vehicle occupant.
 8. The methodof claim 1, further comprising: upon detecting a predetermined mobiledevice identifier, by the processor, altering an operation of thevehicle and generating an alert notification.
 9. The method of claim 1,wherein the vehicle event is detected in conjunction with an on-boarddiagnostic (OBD) connector.
 10. The method of claim 1, furthercomprising: storing, by the processor, the mobile device identifier anddata associated with the mobile device identifier in a cloud dataservice, wherein the mobile device identifier and associations of themobile device identifier are communicated to the cloud data service viaa cellular link.
 11. A computing device configured for monitoringvehicle usage within a vehicle, comprising: a processor; memory inelectronic communication with the processor, wherein the memory storescomputer executable instructions that when executed by the processorcause the processor to perform the steps of: receiving a vehicle eventhistory; detecting a vehicle event; detecting a query from a mobiledevice, the query comprising a Wi-Fi probe request or Bluetooth inquiry;identifying a mobile device identifier from the query; associating themobile device identifier with the vehicle event; and generating an alertnotification based at least in part on the vehicle event history and theassociation.
 12. The computing device of claim 11, wherein the mobiledevice identifier includes any combination of a device serial number,international mobile equipment identity (IMEI) number, mobile equipmentidentifier (MEID), cellular data number (CDN), integrated circuit cardidentifier (ICCID), Wi-Fi media access control (MAC) address, BLUETOOTH®MAC address, BLUETOOTH® global identifier, carrier information, mobiledevice model information, and a list of service set identifiers (SSIDs).13. The computing device of claim 11, wherein the vehicle eventcomprises any combination of vehicle speed, vehicle acceleration,vehicle deceleration, vehicle braking, vehicle gravitational force(g-force), vehicle seat belt use, distance traveled, engine performance,vehicle occupancy, and vehicle location.
 14. The computing device ofclaim 11, wherein the instructions executed by the processor cause theprocessor to perform the steps of: determining whether the mobile deviceis within the vehicle, wherein determining whether mobile device iswithin the vehicle comprises any combination of satisfying a quantity ofqueries threshold, satisfying a query timing threshold, and satisfying asignal strength threshold.
 15. The computing device of claim 11, whereinthe instructions executed by the processor cause the processor toperform the steps of: identifying excessive behavior from the vehicleevent, the excessive behavior comprising any combination of satisfying aspeed threshold, satisfying an acceleration threshold, satisfying adeceleration threshold, satisfying a braking threshold, satisfying ag-force threshold, satisfying a revolutions per minute (RPM) threshold,and satisfying an audio system volume threshold.
 16. The computingdevice of claim 15, wherein the instructions executed by the processorcause the processor to perform the steps of: associating the mobiledevice identifier with the excessive behavior.
 17. The computing deviceof claim 11, wherein the instructions executed by the processor causethe processor to perform the steps of: upon detecting the predeterminedmobile device identifier, altering an operation of the vehicle andgenerating an alert notification.
 18. The computing device of claim 11,wherein the instructions executed by the processor cause the processorto perform the steps of: storing the mobile device identifier and dataassociated with mobile device identifier in a cloud data service,wherein the mobile device identifier and associations of the mobiledevice identifier are communicated to the cloud data service via acellular link.
 19. A non-transitory computer-readable storage mediumstoring computer executable instructions that when executed by aprocessor cause the processor to perform the steps of: detecting avehicle event; detecting a query from a first mobile device and a secondmobile device, the queries each comprising a Wi-Fi probe request orBluetooth inquiry; identifying a mobile device identifier from each ofthe queries; associating the mobile device identifiers with the vehicleevent; and determining whether the first mobile device is within thevehicle by at least one of satisfying a quantity of queries threshold,satisfying a query timing threshold, and satisfying a signal strengththreshold.
 20. The computer-program product of claim 19, wherein themobile device identifier includes any combination of a device serialnumber, international mobile equipment identity (IMEI) number, mobileequipment identifier (MEID), cellular data number (CDN), integratedcircuit card identifier (ICCID), Wi-Fi media access control (MAC)address, BLUETOOTH® MAC address, BLUETOOTH® global identifier, carrierinformation, mobile device model information, and a list of service setidentifiers (SSIDs).